Cerberus [CONFIGURE] options

• 0 : Any nulls in an aggregate will be counted as null when the aggregate is used in a query.
• <> 0 : Any nulls in an aggregate will be counted as 0 when the aggregate is used in a query.

To be used with databases stored on read-only media (such as CD or DVD) where it is not possible for Engine to write the @check@ file to the repository root. Requires a restart of Engine.

If non-zero, decimal points (.) will be displayed as commas (,).

• 0: OFF
• <> 0 : ON

If ON, decimals will be replaced by commas when retrieving results from a Crosstab or when retrieving data from a recordset. Requires a restart of Engine.

20 will set default e.g. 2016; 19 will set default e.g. 1916.

• Min = 1
• Max = 15

DefaultPrecision affects the creation and calculation of REAL Fields, whether as part of a data load process via iLoader, or through creation of dynamic fields as part of data engineering.

Loading Data

When loading data unless otherwise specified, real data will be loaded with a precision of DefaultPrecision:

• Raw Data X.XXXX (precision = 4)
• Loaded Data: X.XX (precision = 2)

However, it is possible to explicitly set the precision prior to the load via

• the iLoader PRECISION keyword,
• or by specifying the precision in the iLoader TABLE_DEFINITION|FORMAT parameter.

If the precision has been explicitly set using one of these methods, it overrides the DefaultPrecision setting, when set to 3:

• Raw Data X.X (precision = 1)
• Loaded Data: X.XXX (precision = 3)

Precision settings truncate (by rounding up), or extend (by adding zeros) as appropriate.

Creating Expressions

When creating expressions, the precision of the resulting REAL field is determined by the parameters in the expression. The highest precision in the expression is used to determine the resulting precision. For example, when set to 2:

• Expression A.AAA B.B
• Loaded Data: X.XXX (precision = 3)

When calculating expressions, the precision can be explicitly set by use of the REAL keyword: REAL([EXPRESSION], [PRECISION])

The delimiter can be specified in one of three ways:

1. Character Literals: Single character entries such as ",", "|" and "!" (without the quotes) will be interpreted literally.
2. Escape Characters: The following double character entries are taken as special characters: "\t" - Tab; "\n" - Line Feed; "\r" - Character Return; "\v" - Vertical tab; "\f" - Form Feed "; \0" - Null Terminator.

3. Character Code: A character code can be specified in either decimal or hex. A hex code must be prefixed by 0x i.e.

4. DelimitedOutputCharacter=0x003e

5. If a unicode character with a high byte set is used on a ansi text dump only the lower byte of the delimiter will be used. Care must be taken with this.

If set to False, all text dumps will be in fixed width format, no matter what the specified delimiter is.

If set to True, the system uses the 'DelimitedOutputCharacter' setting to determine which delimiter character will be used.

Data in the specified X and Y columns (see XPlot and YPlot for further details) may not be at the same scale as that required by a mapping application.

For example, when doing a point plot of data, the mapping application may require data to be in meters. However, the X and Y coordinates may be stored in the Engine database in units of 10 meters.

If no scaling factor was used and the X and Y coordinates were used by the mapping application in their stored form, it is likely that any points which are plotted will be in the wrong location on the map - typically if this happens it looks to the user as if nothing has been plotted on the map when in reality all the data is being plotted somewhere off the edges of the map.

The default value of 10 assumes that data stored in the EASTING and NORTHING columns is in 10s of meters. If it was stored in Kilometers, a DistanceDivisor of 1000 would be required.

The default value is 10 because this is the format of the data shipped with the default database.

• 0: Enhanced Security is OFF.
• 1: Enhanced security is ON.

Requires restart of Engine.

0: Expressions using _TODAY will not be recalculated automatically

<>0: Expressions using _TODAY will be recalculated automatically

Min = 1

Max = 65535

• 0: Links will be stored in the repository folder.
• 1<>0: Where link keys both come from the same database, link files will be stored in the Database folder.

Requires restart of Engine. This can be of use when using Windows file copying to copy Engine databases or transfer database from one repository to another, as any internal links within the database are also copied.

If LocalLinks is not used and data is copied in this way, it will be necessary to rebuild the internal Database links in the copied data.

• 0 : GMT is used as the standard time for logging.
• <>0 : local system time is used for logging.

• 0: Do not rescan the database on start up.
• <>0: Rescan database.

Can be used to resync a database in the event of a failed load.

• 0 : Off - no rounding will take place.
• <>0 : REALs will be rounded to the precision set by the CO_DefaultPrecision setting.

• 0: OFF.
• <>0: ON.

The SELECT INTO syntax is used to output data to a file or table. When outputting to a table, it is possible to automatically include the Engine IURN of the selected records by setting SelectIntoIncludesURN to ON.

SELECT Field1, Field2  
      INTO [DB].[NEWTABLE]

      WHERE Field1="A";

If SelectIntoIncludesURN is ON, the resulting table will contain 3 fields, the first of which will be a field called URN containing the internal record numbers:

• 0: Nulls in aggregates are not stored as zero.
• <>0: Nulls in aggregates are stored as zeros.

In some cases it may be valid to store nulls as zeros. However, this will usually be invalid - for example, consider a situation where you are summing customer profitability by Household. One household may have no customers i.e. null, which would be stored as zero if this setting was switched on. Another household may have two customers with profitability value of +5 and -5 respectively which would be summed to 0. In this scenario a null and a 0 value would be very different.

• 0 : Each table will have its own import error log.
• <>0 : All tables will share the same import error log.

• 0 : Use UO_DateFormat.
• <>0 : Use SO_SystemDate Format.

• 0 : Multiple index jobs will not be run in parallel.
• <>0 : Multiple index jobs will be run in parallel.